Skip to content

Conversation

@ritwik-g
Copy link
Contributor

Related Issues

Related to #17

Changes Made

  • Implemented the add-value-config command to allow users to define new value configurations with metadata
  • Added comprehensive unit tests for the command implementation
  • Added integration tests to verify the command works in a real environment
  • Added unit tests for the CLI interface
  • Created ADR-009 for future enhancement to support custom configuration file paths
  • Created a separate ADR template file for better organization

Testing Done

  • Added unit tests with 100% code coverage for the new command
  • Added integration tests that verify the command works in a real environment
  • Manually tested the command with various options and edge cases
  • Verified error handling for duplicate paths and empty paths

Checklist

  • I have read the CONTRIBUTING guidelines
  • My code follows the project's style guidelines
  • I have added tests that prove my fix/feature works
  • I have updated the documentation accordingly
  • All new and existing tests passed
  • My commits follow the project's commit message convention

Type of Change

  • Feature
  • Bug Fix
  • Documentation
  • Performance Improvement
  • Code Style Update
  • Refactoring
  • CI/CD
  • Other

Breaking Change

  • No
  • Yes (please describe below)

Additional Information

The add-value-config command allows users to define new value configurations with metadata such as description, whether it's required, and whether it's sensitive. This is a key feature for managing Helm values and follows the design outlined in the sequence diagrams and low-level design documents.

Additionally, this PR includes an ADR for a future enhancement to support custom configuration file paths, which will provide more flexibility for users.

This commit implements the add-value-config command, which allows users to define a new value configuration with metadata.

Changes Made:
- Implemented AddValueConfigCommand class with proper validation and error handling
- Updated CLI to register the new command with appropriate options
- Added unit tests with mocks to test the command logic in isolation
- Added integration tests to verify file writing and structure
- Updated tasks.md to mark the task as completed

Testing Done:
- Added unit tests with 100% code coverage
- Added integration tests that verify the command works in a real environment
- Manually tested the command with various options and edge cases

Type of Change: Feature
Breaking Change: No
Added unit tests for the add-value-config CLI function to improve test coverage:
- Test for successful addition of a value configuration
- Test for handling duplicate paths
- Test for handling empty paths

These tests ensure that the CLI interface for the add-value-config command works correctly
and handles error cases appropriately.
- Added ADR-009 for supporting custom configuration file paths
- Created a separate ADR template file
- Updated README.md to reference the template file
- Moved 'Creating New ADRs' section to the top of README.md
Updated the ADR to reference GitHub issue #17 for the custom configuration file paths feature.
@ritwik-g ritwik-g linked an issue Feb 27, 2025 that may be closed by this pull request
@sonarqubecloud
Copy link

@ritwik-g ritwik-g merged commit 36aec3d into main Feb 27, 2025
9 checks passed
@ritwik-g ritwik-g deleted the feature/add-value-config branch February 27, 2025 08:28
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Add cli option to add basic non sensitive values

2 participants